Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enter replicasets from deployments #3001

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rudrakhp
Copy link

@rudrakhp rudrakhp commented Nov 30, 2024

Fixes #2951

Today on entering a deployment, pods associated with it are listed. Changed behaviour to list replicasets instead. Entering replicaset will list the related pods.

Ran make build && ./execs/k9s on a test cluster to validate behaviour.

Signed-off-by: Rudrakh Panigrahi <[email protected]>
Copy link

@dor1202 dor1202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rudrakhp Nice!
I don't think i can review the code, so i will keep it for @derailed 😄 .
IMO, you're right that the replicaset makes more sense on enter press than the pod list. But, we should keep the pod behavior in a different shortcut (like P key if not used) and not removing it. I'm sure it's being used.

Side note, in any case we need to update the docs on the new logic

@rudrakhp
Copy link
Author

rudrakhp commented Dec 1, 2024

I think the deployment --> replicaset --> pods flow is what everyone needs. I don't see a scenario where someone might need a strict deployment --> pods flow. Technically as well, it is replicasets that are associated with deployments and not pods. I will let @derailed pitch in regarding this along with his review, will add a shortcut then if required.

Copy link
Owner

@derailed derailed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rudrakhp Thank you for this PR! Tho technically this is correct, I don't think we should alter the current behavior as this was a conscious decision to get to the pertinent information quickly aka show me the latest incarnation of the pods associated with this deployment.
That said, I think it makes sense to nav dp->rs so users can see the various versions at stake.

@derailed derailed added enhancement New feature or request needs-tlc Pr needs additional updates labels Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-tlc Pr needs additional updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

View replicaset (Revision) from the deployment page
3 participants